home *** CD-ROM | disk | FTP | other *** search
/ IRIX Base Documentation 2001 May / SGI IRIX Base Documentation 2001 May.iso / usr / share / catman / p_man / catD / iovec.z / iovec
Encoding:
Text File  |  1998-10-30  |  4.2 KB  |  67 lines
  1.  
  2.  
  3.  
  4. iiiioooovvvveeeecccc((((DDDD4444))))                                                            iiiioooovvvveeeecccc((((DDDD4444))))
  5.  
  6.  
  7.  
  8. NNNNAAAAMMMMEEEE
  9.      _iiii_oooo_vvvv_eeee_cccc - data storage structure for I/O using _uuuu_iiii_oooo(D4)
  10.  
  11. SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
  12.      _####_iiii_nnnn_cccc_llll_uuuu_dddd_eeee _<<<<_ssss_yyyy_ssss_////_tttt_yyyy_pppp_eeee_ssss_...._hhhh_>>>>
  13.      _####_iiii_nnnn_cccc_llll_uuuu_dddd_eeee _<<<<_ssss_yyyy_ssss_////_uuuu_iiii_oooo_...._hhhh_>>>>
  14.      _####_iiii_nnnn_cccc_llll_uuuu_dddd_eeee _<<<<_ssss_yyyy_ssss_////_dddd_dddd_iiii_...._hhhh_>>>>
  15.  
  16. DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
  17.      The _iiii_oooo_vvvv_eeee_cccc structure describes a data storage area for transfer in a _uuuu_iiii_oooo
  18.      structure.  Conceptually, it may be thought of as a base address and
  19.      length specification.
  20.  
  21. UUUUSSSSAAAAGGGGEEEE
  22.      A separate interface does not currently exist for allocating _iiii_oooo_vvvv_eeee_cccc(D4)
  23.      structures when the driver needs to create them itself.  Therefore, the
  24.      driver may either use _kkkk_mmmm_eeee_mmmm______zzzz_aaaa_llll_llll_oooo_cccc(D3) to allocate them, or allocate them
  25.      statically.
  26.  
  27.    SSSSttttrrrruuuuccccttttuuuurrrreeee DDDDeeeeffffiiiinnnniiiittttiiiioooonnnnssss
  28.      The _iiii_oooo_vvvv_eeee_cccc structure contains the following members:
  29.  
  30.      _cccc_aaaa_dddd_dddd_rrrr______tttt  _iiii_oooo_vvvv______bbbb_aaaa_ssss_eeee_;;;;  _////_**** _bbbb_aaaa_ssss_eeee _aaaa_dddd_dddd_rrrr_eeee_ssss_ssss _oooo_ffff _tttt_hhhh_eeee _dddd_aaaa_tttt_aaaa _ssss_tttt_oooo_rrrr_aaaa_gggg_eeee _aaaa_rrrr_eeee_aaaa _****_////
  31.      _iiii_nnnn_tttt      _iiii_oooo_vvvv______llll_eeee_nnnn_;;;;   _////_**** _ssss_iiii_zzzz_eeee _oooo_ffff _tttt_hhhh_eeee _dddd_aaaa_tttt_aaaa _ssss_tttt_oooo_rrrr_aaaa_gggg_eeee _aaaa_rrrr_eeee_aaaa _iiii_nnnn _bbbb_yyyy_tttt_eeee_ssss _****_////
  32.  
  33.      The driver may only set _iiii_oooo_vvvv_eeee_cccc structure members to initialize them for a
  34.      data transfer for which the driver created the _iiii_oooo_vvvv_eeee_cccc structure.  The
  35.      driver must not otherwise change _iiii_oooo_vvvv_eeee_cccc structure members.  However,
  36.      drivers may read them.  The _iiii_oooo_vvvv_eeee_cccc structure members available to the
  37.      driver are:
  38.  
  39.      _iiii_oooo_vvvv______bbbb_aaaa_ssss_eeee contains the address for a range of memory to or from which data
  40.      are transferred.
  41.  
  42.      _iiii_oooo_vvvv______llll_eeee_nnnn contains the number of bytes of data to be transferred to or from
  43.      the range of memory starting at _iiii_oooo_vvvv______bbbb_aaaa_ssss_eeee.
  44.  
  45. RRRREEEEFFFFEEEERRRREEEENNNNCCCCEEEESSSS
  46.      _pppp_hhhh_yyyy_ssss_iiii_oooo_cccc_kkkk(D3), _uuuu_iiii_oooo_mmmm_oooo_vvvv_eeee(D3), _uuuu_rrrr_eeee_aaaa_dddd_cccc(D3), _uuuu_wwww_rrrr_iiii_tttt_eeee_cccc(D3), _uuuu_iiii_oooo(D4)
  47.  
  48.  
  49.  
  50.  
  51.  
  52.  
  53.  
  54.  
  55.  
  56.  
  57.  
  58.  
  59.  
  60.  
  61.  
  62.  
  63.                                                                         PPPPaaaaggggeeee 1111
  64.  
  65.  
  66.  
  67.